Variable-depth multi device chassis

ABSTRACT

A multi device system includes a rack with a rack slot. A device chassis is positioned in the rack slot. The device chassis includes first device slot with a first device entrance, and a second device slot with a second device entrance. A first device stop member extends from the device chassis and into the first device slot. The distance between the first device stop member and the first device entrance is adjustable, and the first device stop member is configured to move a first device in the first device slot through the first device entrance. A second device stop member extends from the device chassis and into the second device slot. The distance between the second device stop member and the second device entrance is adjustable, and the second device stop member is configured to move a second device in the second device slot through the second device entrance.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a Continuation application to U.S. Utility application Ser. No.14/632,814 filed Feb. 26, 2015, entitled “VARIABLE-DEPTH MULTI DEVICECHASSIS,” Attorney Docket No. 16356.1741, the disclosure of which isincorporated herein by reference in its entirety.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to a multi device chassis that canaccommodate information handling systems with different depths.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems (IHSs). Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Some IHSs such as, for example, servers, switches, and/or other devices,are utilized in racks that hold those devices in one or more slots inthe rack and provide for the interconnection of the devices to eachother. Some devices may be configured to occupy approximately the fullwidth of the slot in the rack (“full width devices”), while some devicesmay be configured to occupy approximately half the width of the slot inthe rack (“half width devices”). To accommodate such half width devices,multi device chassis have been developed that couple to the slot andsecure two of the half width devices in the rack in a single slot.Furthermore, some devices may be configured to occupy approximately thefull depth of the slot in the rack (“full depth devices”), while somedevices may be configured to occupy approximately half the depth of theslot in the rack (“half depth devices”), and some racks may include ahalf width, full depth device as well as a half width, half depthdevice. In such situations, the user is required to position the halfwidth, full depth device in a first multi device chassis that ispositioned in a first slot on the rack and designed to accommodate twohalf width, full depth devices, while positioning the half width, halfdepth device in a second multi device chassis that is positioned in asecond slot on the rack and designed to accommodate two half width, halfdepth devices. As such, space in the rack may be wasted (e.g., when anodd number of either half width, full depth devices or half width, halfdepth devices are included in the rack, resulting in at least one openhalf width space in either or both of the first slot and the second sloton the rack.)

Accordingly, it would be desirable to provide an improved multi devicechassis.

SUMMARY

According to one embodiment, a multi-device coupling system includes amulti-device chassis that defines a first device slot and a seconddevice slot in a side-by-side orientation; a first device stop memberthat extends from the multi-device chassis and into the first deviceslot, wherein a location of the first device stop member along a lengthof the first device slot is adjustable, and wherein the first devicestop member is configured to move a first device that is positioned inthe first device slot out of the first device slot; and a second devicestop member that extends from the multi-device chassis and into thesecond device slot, wherein a location of the second device stop memberalong a length of the second device slot is adjustable, and wherein thesecond device stop member is configured to move a second device that ispositioned in the second device slot out of the second device slot.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an informationhandling system.

FIG. 2 is a perspective view illustrating an embodiment of a rack.

FIG. 3a is a perspective view illustrating an embodiment of amulti-device chassis.

FIG. 3b is a perspective view illustrating an embodiment of amulti-device chassis.

FIG. 3c is a perspective view illustrating an embodiment of amulti-device chassis.

FIG. 3d is a perspective view illustrating an embodiment of a slidingrail on the multi-device chassis of FIGS. 3a -d.

FIG. 3e is a perspective view illustrating an embodiment of a slidingrail on the multi-device chassis of FIGS. 3a -d.

FIG. 3f is an exploded perspective view illustrating an embodiment of adevice stop member on the multi-device chassis of FIGS. 3a -d.

FIG. 3g is a perspective view illustrating an embodiment of the devicestop member of FIG. 3 g.

FIG. 3h is an exploded perspective view illustrating an embodiment of aportion of the sliding rail of FIGS. 3e and 3f with related components.

FIG. 3i is a partially exploded perspective view illustrating anembodiment of the sliding rail of FIGS. 3e and 3f with relatedcomponents.

FIG. 3j is a perspective view illustrating an embodiment of the portionof the sliding rail of FIGS. 3e and 3f with related components.

FIG. 4 is a flow chart illustrating an embodiment of a method forcoupling devices to a device chassis.

FIG. 5a is a perspective view illustrating an embodiment of a devicestop member secured in a first position in the multi-device chassis ofFIGS. 3a -3 d.

FIG. 5b is a perspective view illustrating an embodiment of the devicestop member of FIG. 5a being moved from the first position in themulti-device chassis of FIGS. 3a -3 d.

FIG. 5c is a perspective view illustrating an embodiment of the devicestop member of FIG. 5a moved to a second position in the multi-devicechassis of FIGS. 3a -3 d.

FIG. 5d is a perspective view illustrating an embodiment of the devicestop member of FIG. 5c moved to a second position in the multi-devicechassis of FIGS. 3a -3 d.

FIG. 5e is a perspective view illustrating an embodiment of the devicestop member of

FIG. 5a secured in the second position in the multi-device chassis ofFIGS. 3a -3 d.

FIG. 6a is a perspective view illustrating the multi-device chassis ofFIGS. 3a -3 d prepared for receiving devices.

FIG. 6b is a perspective view illustrating devices being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 6c is a perspective view illustrating devices being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 6d is a perspective view illustrating a device being secured intothe multi-device chassis of FIGS. 3a -3 d.

FIG. 6e is a perspective view illustrating a device being secured intothe multi-device chassis of FIGS. 3a -3 d.

FIG. 7a is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 7b is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 7c is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 7d is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 7e is a side view illustrating a device being secured into themulti-device chassis of FIGS. 3a -3 d.

FIG. 8a is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 8b is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 8c is a side view illustrating a device being retained into themulti-device chassis of FIGS. 3a -3 d.

FIG. 9a is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 9b is a side view illustrating a device being moved into themulti-device chassis of FIGS. 3a -3 d.

FIG. 9c is a side view illustrating a device secured in the multi-devicechassis of FIGS. 3a -3 d.

FIG. 10a is a perspective view illustrating a latch prior to a devicebeing positioned in the multi-device chassis of FIGS. 3a -3 d.

FIG. 10b is a perspective view illustrating a latch being operated tosecure a device in the multi-device chassis of FIGS. 3a -3 d.

FIG. 10c is a perspective view illustrating a latch securing a device inthe multi-device chassis of FIGS. 3a -3 d.

FIG. 11 is a perspective view illustrating devices secured in themulti-device chassis of FIGS. 3a -3 b.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety other mass storage devicesknown in the art. IHS 100 further includes a display 110, which iscoupled to processor 102 by a video controller 112. A system memory 114is coupled to processor 102 to provide the processor with fast storageto facilitate execution of computer programs by processor 102. Examplesof system memory may include random access memory (RAM) devices such asdynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

Referring now to FIG. 2, an embodiment of a rack 200 is illustrated. Asdiscussed in further detail below, the rack 200 is configured to hold aplurality of IHSs such as, for example, the IHS 100 discussed above withreference to FIG. 1. While referred to as a “rack”, the rack 200 may beprovided by a wide variety of structures known in the art that areconfigured to hold a plurality of IHSs. The rack 200 includes a rackchassis 202 having a top portion 202 a, a bottom portion 202 b locatedopposite the rack chassis 202 from the top portion 202 a, a side portion202 c located between the top portion 202 a and the bottom portion 202b, a side potion 202 d location between the top portion 202 a and thebottom portion 202 b and located opposite the rack chassis 202 from theside portion 202 c, and a rear portion 202 e located between the topportion 202 a, the bottom portion 202 b, and the sides portions 202 cand 202 d. A plurality of rack slots 204 are defined by the rack chassis202 between the top portion 202 a, the bottom portion 202 b, the sidesportions 202 c and 202 d, and the rear portion 202 e, by a plurality ofIHS coupling features 206 on the rack chassis 202. Each of the rackslots 204 includes a rack entrance that is located opposite the rackslot 204 from the rear portion 202 e of the rack chassis 202. As isknown in the art, the top portion 202 a, the bottom portion 202 b, thesides portions 202 c and 202 d, and/or the rear portions 202 e, and/ mayinclude features for routing, securing, directing, and/or otherwisecoupling devices and device chassis in the device slots 204, as well ascable routing features, security features, and/or other rack featuresknown in the art. As is known in the art, each of the rack slots 204 ismay be configured to house a full width device (e.g., a device, such asthe IHS 100 of FIG. 1, that is approximately the width of the rack slot204 (i.e., slightly less than) as measured between the sides portions202 c and 202 d).

Referring now to FIGS. 3a, 3b, 3c, 3d, 3e, 3f, 3g, 3h, 3i, 3j, and 3k ,an embodiment of a multi-device chassis 300 (hereinafter “device chassis300”) is illustrated. In the illustrated embodiment, the device chassis300 is illustrated as a multi device chassis that allows two devices tobe positioned in and secured to the device chassis 300 in a side-by-sideorientation. However, the teachings of the present disclosure may beused to provide more than two devices in a side-by-side orientation, ora plurality of devices in a stacked orientation (i.e., one on top of theother). As such, the specific embodiment illustrated and described belowis not meant to limit the teachings of the present disclosure to theillustrated system, and one of skill in the art will recognize thatthose teachings may be applied to a variety of multi-device scenarioswhile remaining within the scope of the present disclosure.

Referring initially to FIG. 3a , the device chassis 300 includes base302 having a bottom wall 302 a, a pair of side walls 302 b and 302 cthat extend from opposite edges of the bottom wall 302 a such that theyare opposite the base 302 from each other, a rear wall 302 d thatextends between the bottom wall 302 a and the side walls 302 b and 302c, a top wall portion 302 e that extends between the side walls 302 band 302 c opposite the base 302 from the bottom wall 302 a, as well as atop wall portion 302 f that extends between the side walls 302 b and 302c and the rear wall 302 d opposite the base 302 from the bottom wall 302a. An intermediate wall 302 g extends between the bottom wall 302 a, therear wall 302 d, and the top wall portions 302 e and 302 f, and islocated approximately midway between the side walls 302 b and 302 c. Afirst device slot 304 is defined between the bottom wall 302 a, the topwall portions 302 e and 302 f, the side wall 302 b, the intermediatewall 302 g, and the rear wall 302 d. The first device slot 304 includesa first device entrance 304 a that is located opposite the first deviceslot 304 from the rear wall 302 d of the base 302. A second device slot306 is defined between the bottom wall 302 a, the top wall portions 302e and 302 f, the side wall 302 b, the intermediate wall 302 g, and therear wall 302 d. The second device slot 306 includes a second deviceentrance 306 a that is located opposite the second device slot 306 fromthe rear wall 302 d of the base 302.

While illustrated with an open top (via top wall portions 302 e and 302f), the base 302 of the device chassis 300 may completely enclose thefirst device slot 304 and the second device slot 306, or may includeother open walls (e.g., the top wall 302 a, the side walls 302 b and 302c, the rear wall 302) that are similar to the top wall portions 302 eand 302 f to provide, for example, cable routing or access as desired.However, in experimental embodiment, the top wall portions 302 e and 302f have been found to provide rigidity for the device chassis sufficientfor coupling to the devices and the rack, as discussed below, while alsoproviding for access to devices when they are positioned in the devicechassis 300 to, for example, access the rear of the device for cablingor other connection features, and for the ability to remove the devicefrom the device chassis 300.

A plurality of device coupling members 308, described in further detailbelow, are included adjacent the first device slot 304 and the seconddevice slot 306. In the illustrated embodiment, a device coupling member308 is coupled to the side wall 302 b such that it is located betweenthe side wall 302 b and the first device slot 304, a device couplingmember 308 is coupled to the intermediate wall 302 g such that it islocated between the intermediate wall 302 g and the first device slot304, a device coupling member 308 is coupled to the intermediate wall302 g such that it is located between the intermediate wall 302 g andthe second device slot 306, and a device coupling member 308 is coupledto the side wall 302 c such that it is located between the side wall 302c and the second device slot 306. In the embodiments illustrated inFIGS. 3a-3d , some features of the device coupling members 308 are notcalled out for clarity of illustration, and those features are calledout and discussed with reference to the other figures below. Asdiscussed below, each of the device coupling members 308 may besubstantially similar, and thus the discussion of the structure andoperation of the device coupling member 308 below may apply to any ofthe device coupling members 308 in the device chassis 300. However, thatdiscussion should not be interpreted as limiting the device couplingmembers 308 in the device chassis 300 to identical device couplingsystems, as some modification of the device coupling members 308 (e.g.,for different sizes, types, orientations, or designs of device chassis)will fall within the scope of the present disclosure.

As illustrated in FIGS. 3b and 3c , a plurality of rack couplings 310may be coupled to the device chassis 300. For example, a rack coupling310 may be coupled to the side wall 302 b opposite the side wall 302 bfrom the first device slot 304, and a rack coupling 310 may be coupledto the side wall 302 c opposite the side wall 302 c from the seconddevice slot 306. In an embodiment, each of rack couplings 310 includesengagement features for engaging and moveably coupling the devicechassis 300 to the rack 200 in one of the rack slots 204, discussedabove with reference to FIG. 2, as well as a securing feature 310 a forsecuring the device chassis 300 in one of the rack slots 204. With therack couplings 310 coupled to the device chassis 300, the device chassis300 may be moved through one of the rack entrances to be positioned itsassociated rack slot 204, and secured to the rack chassis 202 byengaging the securing feature 310 a with a corresponding feature on therack chassis 202.

Referring now to FIGS. 3d and 3e , an exploded view of one of the devicecoupling members 308 is provided. The device coupling member 308includes an outer spring housing 308 a that is mounted, in theillustrated embodiment, to the side wall 302 b of the device chassis 300adjacent the rear wall 302 d such that the outer spring housing 308 a islocated between the side wall 302 b and the first device slot 304. Aninner spring housing 308 b houses a spring 308 c and is coupled to theouter spring housing 308 a to position the spring 308 c in the outerspring housing 308 a while allowing the spring to extend out of both theouter spring housing 308 a and the inner spring housing 308 b. With theinner spring housing 308 b positioned in the outer spring housing 308 a,the spring 308 c may engage the rear wall 302 d of the device chassis300 or other bracing feature (e.g., the outer spring housing 308 a or afeature extending from the side wall 302 b) to allow the spring toprovide the biasing force discussed below.

A sliding rail 308 d is moveably coupled, in the illustrated embodiment,to the side wall 302 b via, for example, a track on the side wall 302 band track coupling features on the sliding rail 308 d that allow thesliding rail 308 d to move relative to the side wall 302 b such that thesliding rail 308 d may be housed in and then extended out of the firstdevice entrance 304 a, discussed in further detail below. As discussedbelow, the sliding rail 308 d defines a channel that includes aplurality of stop features that are not clearly visible in FIGS. 3d and3e . The sliding rail 308 a may be coupled to or otherwise engaged withthe spring 308 c such that the spring 308 c may provide a biasing forceon the sliding rail 308 d that biases the sliding rail 308 a towards thefirst device entrance 304 a. In different embodiments, differentmaterials and manufacturing techniques may be used for the sliding rail308 d, including injection molding plastic materials to produce thesliding rails 308 d, forming sheet metal to produce the sliding rails308 d, casting or forging metal materials to produce the sliding rails308 d, extruding and machining metals or plastics to produce the slidingrails 308 d, and/or a variety of other manufacturing techniques on avariety of other materials known in the art.

A device stop member 310 is moveably coupled to the sliding rail 308 a.In the embodiments illustrated in FIGS. 3d and 3e , some features of thedevice stop member 310 are not called out for clarity of illustration,and those features are called out and discussed with reference to theother figures below. A device retention member 312 is moveably coupledto the sliding rail 308 a. In the embodiments illustrated in FIGS. 3dand 3e , some features of the device retention member 312 are not calledout for clarity of illustration, and those features are called out anddiscussed with reference to the other figures below. A latch 314 ismoveably coupled to an end of the sliding rail 308 a (e.g., the end ofthe sliding rail 308 a that is opposite the end of the sliding rail 308d that engages the spring 308 c in the illustrated embodiment). In theembodiments illustrated in FIGS. 3d and 3e , some features of the latch314 are not called out for clarity of illustration, and those featuresare called out and discussed with reference to the other figures below.While in the embodiments discussed below, the sliding rails moverelative to the device chassis 300, one of skill in the art inpossession of the present disclosure will recognize that the slidingrails may be replaced with fixed rails (i.e., not moveable relative tothe device chassis 300), and the devices may engage the fixed rails tocouple the devices to the device chassis 300 similarly as describedbelow. However, in experimental embodiments, sliding rails have beenfound to provide benefits with regard to coupling devices to the devicechassis 300, as well as enabling different types of devices to becoupled to the device chassis (due to the modularity of the slidingrails).

Referring now to FIGS. 3f and 3g , an embodiment of the device stopmember 310 is illustrated. The device stop member 310 includes asecuring base 310 a defining a coupling aperture 310 b on a first end. Apair of securing members 310 c and 310 d extend from opposite sides of asecond end of the securing base 310 a, and a handle coupling 310 eextends from the second end of the securing base 310 a in asubstantially perpendicular orientation to the securing base 310 a andthe securing members 310 c. The device stop member 310 includes a handle310 f that may be coupled to the handle coupling 310 e, and a slideplate 310 g that defines an aperture 310 h. A rivet 310 i may be used tocouple the device stop member 310 to the sliding rail 308 d bypositioning the rivet 310 i in each of the apertures 310 b and 310 h(illustrated in FIG. 3g without the sliding rail 308 d present) when thesecuring base 310 a and the slide plate 310 g are located on oppositesides of the sliding rail 308 d, as discussed in further detail below.

Referring now to FIGS. 3h, 3i, and 3j , the sliding rail 308 d isillustrated with some of the features discussed above. FIG. 3hillustrates how the sliding rail 308 d defines a channel 316 includingfull depth stop features 316 a that are located an end of the slidingrail 308 d, and half depth stop features 316 b that are locatedapproximately halfway along the length of the sliding rail 308 d. Whileonly two stop features are illustrated, the channel 316 may include anynumber of stop features, and/or other types of stop features that allowthe device stop member to be moved to and secured along any portion ofthe length of the sliding rail 308 d, discussed in further detail below.

FIGS. 3h illustrates the device retention member 312 that includes apivotal coupling 312 a and a device engagement surface 312 b, discussedin further detail below. As illustrated in FIG. 3i , the deviceretention member 312 may be moveably coupled to the sliding rail 308 dvia the pivotal coupling 312 a. FIG. 3h also illustrates the latch 314that includes a pivotal coupling 314 a to a sliding rail coupling 314 b,as well as a handle 314 c and a cam mechanism 314 d, discussed infurther detail below. As illustrated in FIG. 3i , the latch 314 may becoupled to the sliding rail 308 d through the connection of the slidingrail coupling 314 b to the sliding rail 308 a (e.g., via screws in theillustrated embodiment). FIGS. 3h, 3i, and 3j also illustrated thedevice stop member 310, with FIG. 3i illustrating how the handle 310 fmay be coupled to the handle coupling 310 e, and the securing base 310 aplaced on an opposite side of the sliding rail 308 d from the slideplate 310 g. As illustrated in FIG. 3i , the slide plate 310 g may thenbe positioned in a track defined by the sliding rail 308 d, and coupledto the securing base 310 substantially as discussed above by extendingthe rivet 310 i through the apertures 310 b, 310 h, and the channel 316defined by the sliding rail 308 d. The coupling of the slide plate 310 gto the securing base 310 in this manner allows the device stop member310 to move along at least a portion of the length of the sliding rail308 d (e.g., through the channel 316), as discussed in further detailbelow. In some embodiment, a detent feature may be provided between thelatch 314 and the sliding rail 308 d in order to retain the latch 314 ina latched position, discussed in further detail below.

Referring now to FIG. 4, a method 400 for coupling devices to a chassisis illustrated. The method 400 begins at block 402 where the devicechassis is coupled to the rack. In an embodiment, the device chassis 300illustrated in FIGS. 3c (e.g., including the rack couplings 310) ismoved through the rack entrance of one of the plurality of rack slots204 in the rack chassis 202 such that it enters that rack slot 204. Forexample, the device chassis 300 may be aligned with a rack entrance on arack slot 204 such that the rack couplings 310 on the device chassis 300are aligned with coupling features (e.g., tracks) on the rack chassis202 adjacent the rack slot 204, and moved through the rack entrance suchthat the rack couplings 310 engage the coupling features on the rackchassis 202. Following engagement of the rack couplings 310 with thecoupling features on the rack chassis 202, further movement of thedevice chassis 300 through the rack slot 204 is guided by thatengagement until the device chassis 300 is fully seated in the rack slot204 and the securing features 310 a may be engaged with the rack chassis202 to secure the device chassis 300 to the rack 200. As such, a usermay select one of the rack slots 204 in the rack 200 that they wouldlike to position half-width devices, and perform block 402 of the method400 to couple the device chassis 300 to the rack 200 as described above.Furthermore, a plurality of the device chassis 300 may be coupled todifferent rack slots 204 in the rack 200 if the user would like toposition additional half-width devices in the rack 200. One of skill inthe art in possession of the present disclosure will recognize thatwhile the teachings of the present disclosure provide a device chassis400 that is coupled to a conventional rack to enable the coupling ofdevices to the device chassis 300/rack, the features discussed above onthe device chassis 300 may be integrated into a rack/rack chassis suchthat half width devices may be directed coupled to the rack 200 withoutthe use of the device chassis 300 while remaining within the scope ofthe present disclosure.

The method 400 then proceeds to block 404 where device stop member(s)are adjusted. Referring now to FIGS. 5a, 5b, 5c, 5d, and 5e , anembodiment of adjusting a device stop member 310 on a device couplingmember 308 is illustrated. In the illustrated embodiment, the devicestop member 310 is secured in a first position A along the length of thesliding rail 308 d due to the securing members 310 c and 310 d on thesecuring base 310 a being seated in the full depth stop feature 316 a ofthe channel 316 defined by the sliding rail 308 d, as illustrated inFIG. 5a . In the first position A, the device stop member 310 isconfigured to operate with a half width, full depth device, as discussedin further detail below. In order to adjust the position of the devicestop member 310, a user may engage the handle 310 f and move the devicestop member 310 in a direction B in order to cause the securing members310 c and 310 d on the securing base 310 a to become unseated from thefull depth stop feature 316 a of the channel 316 defined by the slidingrail 308 d, as illustrated in FIG. 5b . The user may then use the handle310 f to move the device stop member 310 in a direction C, and with thesecuring members 310 c and 310 d unseated from the full depth stopfeature 316 a, the device stop member 310 will move through the channel316 defined by the sliding rail 308 d, as illustrated in FIG. 5c . Theuser may continue to move the device stop member 310 in the direction Cuntil the securing members 310 c and 310 d on the securing base 310 aare located adjacent the half depth stop feature 316 b of the channel316 defined by the sliding rail 308 d, as illustrated in FIG. 5d . Theuser may then release the handle 310 f to allow the device stop member310 to move in a direction D such that the securing members 310 c and310 d on the securing base 310 a become seated in the half depth stopfeature 316 b of the channel 316 defined by the sliding rail 308 d tosecure the device stop member 310 in a second position E along thelength of the sliding rail 308 d, as illustrated in FIG. 5e . In thesecond position E, the device stop member 310 is configured to operatewith a half width, half depth device, as discussed in further detailbelow. Adjustment of the device stop member 310 from the second positionE to the first position A operates in the reverse of that discussedabove (e.g., unseat the device stop member 310 from the half depth stopfeature 316 b, move the device stop member 310 adjacent the full depthstop feature 316 a, and seat the device stop member 310 in the fulldepth stop feature 316 a). While the securing of the device stop member310 in the stop features 316 b and 316 c is illustrated and describedusing the securing members 310 c and 310 d, other features may be usedto provide similar functionality. For example, a plunger or other devicemay be extendable from the device stop member 310 to engage stopfeatures in the channel 316 and provide the functionality discussedabove.

Thus, a user may adjust device stop members 310 on the device chassis300 to configure each of the first device slot 304 and the second deviceslot 306 in the device chassis 300 to operate with either half width,full depth devices or half width, half depth devices. In the illustratedembodiment, the user may adjust the device stop members 310 on each sideof a device slot (e.g., e.g., the device stop members 310 extending fromthe side wall 302 b and the intermediate wall 302 g and into the firstdevice slot 304) in which a device is to be positioned. However, in someembodiments, a single device stop member 310 may be sufficient toconfigure a device slot to receive a device and provide thefunctionality discussed below. Furthermore, as discussed above, whilethe illustrated embodiment only includes features for either half width,full depth devices or half width, half depth devices, features thatprovide for the movement and securing of the device stop members at anylocation along the length of the sliding rail 308 d that is needed toaccommodate a device (e.g., a half width, ¾ depth device, a half width,¼ depth device, any half width device with a depth less than the fulldepth of the rack slot/device slot, etc.) are envisioned as fallingwithin the scope of the present disclosure. As such, at block 404, theuser may adjust the device stop members 310 for any device slot in anydevice chassis 300 in the rack 200 to accommodate a half width devicewith a depth for which the device slot is not currently configured.

The method 400 then proceeds to block 406 where device(s) are secured inthe device chassis. Referring now to FIGS. 6a, 6b, 6c, 6d, 6e, and 6f ,a plurality of devices are illustrated as being secured in a devicechassis. Furthermore, FIGS. 7a, 7b, 7c, 7d, 7e, 8a, 8b, 8c, 9a, 9b, 9c ,10 a, 10 b, 10 c, and 11 are provided to show detail of the functioningof the components of the device chassis 300 in securing devices in thedevice chassis 300. Referring first to the embodiment illustrated inFIG. 6a , the first device slot 304 on the device chassis 300 has beenconfigured at block 404 for half depth devices by adjusting the devicestop members 310 as discussed above, while the second device slot 306 onthe device chassis 300 has been configured at block 404 for full depthdevices by adjusting the device stop members 310 as discussed above. Ascan be seen in FIG. 6a , with no devices in the first device slot 304and the second device slot 306, the springs 308 c provide the biasingforce on the sliding rails 308 d that moves the sliding rails relativeto the device chassis 300 along the moveable coupling therebetween, andcauses the ends of the sliding rails 308 d (e.g., the ends of thesliding rails 308 d to which the latches 314 are coupled) to extend pastthe first device entrance 304 a and the second device entrance 306 a.The device chassis 300 may be prepared to receive devices by rotatingthe latches 314 about their pivotal couplings 314 a such that each ofthe latches are in an unlatched position, illustrated in FIG. 6 a.

Referring now to FIG. 6b , a half depth device 600 is positionedadjacent the first device slot 304 such that the rear of the half depthdevice 600 is located adjacent the first device entrance 304 a, and afull depth device 602 is positioned adjacent the first device slot 304such that the rear of the half depth device 600 is located adjacent thefirst device entrance 304 a. The half depth device 600 and the fulldepth device 602 may then be moved through the first device entrance 304a and the second device entrance 306 a, respectively, and into the firstdevice slot 304 and the second device slot 306. FIG. 7a illustrates howfeatures on the half depth device 600 may engage the channel 316 on thesliding rail 308 d as the half depth device 600 is moved into the firstdevice slot 304 to help guide the half depth device 600 into the firstdevice slot 304, and one of skill in the art in possession of thepresent disclosure will recognize that the full depth device 602 mayinclude similar features and operate in a similar manner when beingmoved into the second device slot 306.

Referring now to FIGS. 6c , the half depth device 600 and the full depthdevice 602 are illustrated has substantially positioned in the firstdevice slot 304 and the second device slot 306. In an embodiment, thepositioning of the half depth device 600 and the full depth device 602illustrated in FIG. 6c shows the half depth device 600 moved into thefirst device slot 304 such that the half depth device 600 engages thedevice stop members 310 but does not provide a force on the device stopmembers 310 that is transferred to the sliding rails 308 d to compressthe springs 308 c, and shows the full depth device 602 moved into thesecond device slot 306 such that the full depth device 602 engages thedevice stop members 310 and provides a force on the device stop members310 that is transferred to the sliding rails 308 d to begin compressingthe springs 308 c (e.g., the user is pushing on the full depth device602 and causing the springs 308 c to compress.)

Referring now to FIGS. 7a, 7b, 7c, 7d, 8a, 8b, 8c, 9a, 9b, and 9c , themovement of the half depth device 600 in the device slot 304 isillustrated and described. FIGS. 7b, 8a, and 9a illustrate the devicechassis 300 as the half depth device 600 just begins to provide a forceon the device stop members 310. As can be seen in FIGS. 7b and 8a , thedevice stop member 310 is configured for half depth devices (e.g., theslide plate 310 g is positioned halfway along the length of the slidingrail 308 d). In this position, the device retention member 312 is spacedapart from a device retention ramp 700 that is located on the bottomwall 302 a of the device chassis 300. FIG. 9a illustrates the spring 308c just beginning to be compressed by the sliding rail 308 d (through theforce transmitted from the user, to the half depth device 600, to thedevice stop member 310, and to the sliding rail 308 d).

FIGS. 7c, 8b, and 9b illustrate the device chassis 300 as the half depthdevice 600 is pushing the device stop members 310 through the firstdevice slot 304. As can be seen in FIGS. 7c and 8b , the deviceretention member 312 has moved towards the device retention ramp 700that is located on the bottom wall 302 a of the device chassis 300,which causes the device retention member 312 to rotate about its pivotalconnection 312 a to the sliding rail 308 d. FIG. 9b illustrates thespring 308 c being further compressed by the sliding rail 308 d (throughthe force transmitted from the user, to the half depth device 600, tothe device stop member 310, and to the sliding rail 308 d).

FIGS. 7d, 8c, and 9c illustrate the device chassis 300 as the half depthdevice 600 has become substantially fully positioned in the first deviceslot 304. As can be seen in FIGS. 7d and 8c , the device retentionmember 312 has moved up the device retention ramp 700 that is located onthe bottom wall 302 a of the device chassis 300, which causes the deviceretention member to further rotate about its pivotal connection 312 a tothe sliding rail 308 d such that the device engagement surface 312 b onthe device retention member 312 engages the feature on the half depthdevice 600 that is located in the channel 316. With the deviceengagement surface 312 b engaging the feature on the half depth device600 that is located in the channel 316, the movement of the half depthdevice 600 towards the first device entrance 304 a is resisted by thedevice retention member 312. FIG. 9c illustrates the spring 308 ccompressed by the sliding rail 308 d (through the force transmitted fromthe user, to the half depth device 600, to the device stop member 310,and to the sliding rail 308 d) when the half depth device 600 issubstantially fully positioned in the first device slot 304. Referringto FIGS. 9a-c , a dampener may be provided on the spring 308 c in orderto control the force provided on the sliding rail 308 d and thus thespeed at which the sliding rail 308 d moves the device out of the deviceslot.

Referring now to FIGS. 10a, 10b, and 10c , the operation of the latch314 is illustrated in detail. FIG. 10a illustrates the latch in anunlatched position (also illustrated in FIGS. 6a, 6b, 6c, 6d (for thehalf depth device 600), 7 a, 7 b, 7 c, and 7 d) with the end of thesliding rail 308 d extending past the first device entrance 304 a andthe second device entrance 306 a. FIG. 10b illustrates the sliding rail308 d no longer extended past the first device entrance 304 a and thesecond device entrance 306 a (e.g., when the device is substantiallyfully positioned in the device slot, as illustrated in FIG. 7d ), andthe latch partially rotated about the pivotal coupling 314 a (e.g.,using the handle 314 c). FIGS. 10b and 10c illustrate how rotation ofthe latch 314 about the pivotal coupling causes the cam mechanism 314 dto engage a feature on the device chassis 300. When the cam feature 314d is fully engaged with the feature on the device chassis 300 asillustrated in FIG. 10c , the movement of the sliding rail 308 drelative to the device chassis 300 is resisted, thus securing the devicein the device slot. One of skill in the art will recognize thatactivation of the latches 314 to secure the half depth device 600 andthe full depth device 602 in the first device slot 304 and the seconddevice slot 306, respectively, may slightly move each of the half depthdevice 600 and the full depth device 602 further into the first deviceslot 304 and the second device slot 306, respectively (thus moving thehalf depth device 600 and the full depth device 602 from beingsubstantially fully positioned in the first device slot 304 and thesecond device slot 306, respectively, to being fully positioned in thefirst device slot 304 and the second device slot 306.) FIG. 11illustrates a view of each of the half depth device 600 and the fulldepth device fully positioned in first device spot 304 and the seconddevice slot 306.

The method 400 then proceeds to block 408 where device(s) are removedfrom the device chassis. In an embodiment, devices may be removed from adevice slot in the device chassis 300 by deactivating the latches 310that resist movement of the sliding rails 308 d adjacent that deviceslot. For example, referring to FIGS. 10a, 10b, and 10c , the latch maybe deactivated from the latched position illustrated in FIG. 10c (withthe cam mechanism 314 d engaging the feature on the device chassis 300)by engaging the handle 314 c to rotate the latch 314 to the positionillustrated in FIG. 10b such that the cam mechanism 314 d disengages thefeature on the device chassis 300. Disengagement of the cam mechanism314 d and the feature on the device chassis 300 removes thecounteracting force on the spring 308 c such that the biasing force fromthe spring 308 c on the sliding rail 308 d may move the sliding rail 308d from the position illustrated in FIGS. 7d and 9c , to the positionillustrated in FIGS. 7c and 9b , and to the position illustrated inFIGS. 7b and 9a . Movement of the sliding rails 308 d results in thehandles 310 f on the device stop members 310 transferring the biasingforce from the spring 308 c to the device in their associated deviceslot. As such, release of the latches 310 on each side of a device thatis located in a device slot on the device chassis 300 causes the deviceto be moved through the device entrance of that device slot. Forexample, FIGS. 6e and 7e illustrate the half depth device 600 secured inthe first device slot 304 with the latches 314 in the latched position.FIGS. 6d and 7d, 7c, and 7b (in that order), illustrate how unlatchingthe latches 314 causes the spring to provide the biasing force and movethe half depth device 600 through the first device entrance 304 a on thefirst device slot 304. As such, a user may then easily grasp the halfdepth device 600 and completely remove it from the first device slot304. One of skill in the art will recognize that the full depth device602 may be removed from the device chassis 300 in substantially the samemanner (i.e., via release of the latches 314 to have the full depthdevice 602 moved via the spring biasing force out of the second deviceentrance 306 a).

Thus, a multi-device coupling system has been described that allows formultiple devices having different depths to be positioned side-by-sidein a rack slot and secured in the rack, while providing for movement ofeach of those devices out of the rack slot when the devices areunsecured (e.g., via a latch) to allow a user to easily grasp the deviceand remove it from the rack slot. As such, rack slots may be optimizedwith both full depth devices and half depth device (or otherless-than-full depth devices), rather than having to dedicate one rackslot to only half width, full depth devices and dedicate another rackslot to only half width, half depth devices. While the systems andmethods above have been described as being used with informationhandling systems and other computing devices, the functionality of themulti-device chassis may be used to couple a container to themulti-device chassis. For example, a first slot in the multi devicechassis may be used to couple an IHS to the multi-device chassis, whilea second slot in the multi-device chassis may be used to couple acontainer to the multi-device chassis for the storage of tools,documentation, spare parts, etc.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. A multi-device system, comprising: a rack thatdefines a rack slot; a device chassis that is positioned in the rackslot, wherein the device chassis defines a first device slot, andwherein the device chassis defines a second device slot that is locatedadjacent the first device slot; a first device coupling subsystemprovided on the device chassis adjacent the first device slot, whereinthe first device coupling subsystem is configured to: couple, inresponse to a first device being positioned in the first device slot,the first device and the device chassis; and decouple the first deviceand the device chassis such that the first device may be removed fromthe first device slot; and a second device coupling subsystem providedon the device chassis adjacent the second device slot, wherein thesecond device coupling subsystem is configured to: couple, independentlyof the coupling and decoupling of the first device and the devicechassis and in response to a second device being positioned in thesecond device slot, the second device and the device chassis; anddecouple, independently of the coupling and decoupling of the firstdevice and the device chassis, the second device and the device chassissuch that the second device may be removed from the second device slot.2. The system of claim 1, wherein: the first device coupling subsystemis configured to provide for the securing of the first device to thedevice chassis and in the first device slot; and the second devicecoupling subsystem is configured to provide for the securing of thesecond device to the device chassis and in the second device slot. 3.The system of claim 1, further comprising: at least one first devicepositioning member that is located on the device chassis adjacent thefirst device slot and that is configured to engage the first device tolocate the first device in the first device slot and immediatelyadjacent a first device entrance of the first device slot; and at leastone second device positioning member that is located on the devicechassis adjacent the second device slot and that is configured to engagethe second device to locate the second device in the second device slotand immediately adjacent a second device entrance of the second deviceslot.
 4. The system of claim 3, wherein: the position of the at leastone first device positioning member is adjustable along a length of thefirst device slot; and the position of the at least one second devicepositioning member is adjustable along a length of the second deviceslot.
 5. The system of claim 1, wherein: a first device couplingsubsystem is provided as a tool-less subsystem that is configured toprovide for the coupling and decoupling of the second device and thedevice chassis without the use of a tool; and a second device couplingsubsystem is provided as a tool-less subsystem that is configured toprovide for the coupling and decoupling of the second device and thedevice chassis without the use of a tool.
 6. The system of claim 1,further comprising: at least one spring-loaded member that is includedin the first device coupling subsystem and that is configured to utilizea spring force to move the first device at least partially out of thefirst device slot when the first device coupling subsystem is used todecouple the first device and the device chassis; and at least onespring-loaded member that is included in the second device couplingsubsystem and that is configured to utilize a spring force to move thesecond device at least partially out of the second device slot when thesecond device coupling subsystem is used to decouple the second deviceand the device chassis.
 7. The system of claim 1, wherein: the seconddevice coupling subsystem providing for the coupling and decoupling ofthe second device and the device chassis independently of the couplingand decoupling of the first device and the device chassis includes thesecond device coupling subsystem allowing, independently of the firstdevice being moved into the device chassis and secured in the firstdevice slot as well as unsecured from the device chassis and removedfrom the first device slot, the second device to be moved into thedevice chassis and secured in the second device slot as well asunsecured from the device chassis and removed from the second deviceslot.
 8. A multi-device coupling system, comprising: a multi-devicechassis that defines a first device slot and a second device slot in aside-by-side orientation; a first device coupling subsystem provided onthe multi-device chassis adjacent the first device slot, wherein thefirst device coupling subsystem is configured to: couple, in response toa first device being positioned in the first device slot, the firstdevice and the multi-device chassis; and decouple the first device andthe multi-device chassis such that the first device may be removed fromthe first device slot; and a second device coupling subsystem providedon the multi-device chassis adjacent the second device slot, wherein thesecond device coupling subsystem is configured to: couple, independentlyof the coupling and decoupling of the first device and the devicechassis and in response to a second device being positioned in thesecond device slot, the second device and the device chassis; anddecouple, independently of the coupling and decoupling of the firstdevice and the device chassis, the second device and the device chassissuch that the second device may be removed from the second device slot.9. The system of claim 8, wherein: the first device coupling subsystemis configured to provide for the securing of the first device to themulti-device chassis and in the first device slot; and the second devicecoupling subsystem is configured to provide for the securing of thesecond device to the multi-device chassis and in the second device slot.10. The system of claim 8, further comprising: at least one first devicepositioning member that is located on the multi-device chassis adjacentthe first device slot and that is configured to engage the first deviceto locate the first device in the first device slot and immediatelyadjacent a first device entrance of the first device slot; and at leastone second device positioning member that is located on the multi-devicechassis adjacent the second device slot and that is configured to engagethe second device to locate the second device in the second device slotand immediately adjacent a second device entrance of the second deviceslot..
 11. The system of claim 10, wherein: the position of the at leastone first device positioning member is adjustable along a length of thefirst device slot; and the position of the at least one second devicepositioning member is adjustable along a length of the second deviceslot.
 12. The system of claim 8, wherein: a first device couplingsubsystem is provided as a tool-less subsystem that is configured toprovide for the coupling and decoupling of the second device and themulti-device chassis without the use of a tool; and a second devicecoupling subsystem is provided as a tool-less subsystem that isconfigured to provide for the coupling and decoupling of the seconddevice and the multi-device chassis without the use of a tool.
 13. Thesystem of claim 8, further comprising: at least one spring-loaded memberthat is included in the first device coupling subsystem and that isconfigured to utilize a spring force to move the first device at leastpartially out of the first device slot when the first device couplingsubsystem is used to decouple the first device and the device chassis;and at least one spring-loaded member that is included in the seconddevice coupling subsystem and that is configured to utilize a springforce to move the second device at least partially out of the seconddevice slot when the second device coupling subsystem is used todecouple the second device and the multi-device chassis.
 14. The systemof claim 10, wherein: the second device coupling subsystem providing forthe coupling and decoupling of the second device and the multi-devicechassis independently of the coupling and decoupling of the first deviceand the multi-device chassis includes the second device couplingsubsystem allowing, independently of the first device being moved intothe multi-device chassis and secured in the first device slot as well asunsecured from the multi-device chassis and removed from the firstdevice slot, the second device to be moved into the multi-device chassisand secured in the second device slot as well as unsecured from themulti-device chassis and removed from the second device slot.
 15. Amethod for coupling devices to a chassis, comprising: providing a devicechassis that defines a first device slot and a second device slot in aside-by-side orientation; coupling, using a first device couplingsubsystem provided on the device chassis adjacent the first device slotand in response to a first device being positioned in the first deviceslot, the first device and the device chassis; decoupling, using thefirst device coupling subsystem provided on the device chassis adjacentthe first device slot, the first device and the device chassis such thatthe first device may be removed from the first device slot; andcoupling, using a second device coupling subsystem provided on thedevice chassis adjacent the second device slot and in response to asecond device being positioned in the second device slot, the seconddevice and the device chassis independently of the coupling anddecoupling of the first device and the device chassis; and decoupling,using the second device coupling subsystem provided on the devicechassis adjacent the second device slot and independently of thecoupling and decoupling of the first device and the device chassis, thesecond device and the device chassis such that the second device may beremoved from the second device slot.
 16. The method of claim 15, furthercomprising: engaging, using at least one first device positioning memberthat is located on the device chassis adjacent the first device slot,the first device to locate the first device in the first device slot andimmediately adjacent a first device entrance of the first device slot;and engaging, using at least one second device positioning member thatis located on the device chassis adjacent the second device slot, thesecond device to locate the second device in the second device slot andimmediately adjacent a second device entrance of the second device slot.17. The method of claim 15, further comprising: adjusting the positionof the at least one first device positioning member along a length ofthe first device slot; and adjusting the position of the at least onesecond device positioning member along a length of the second deviceslot.
 18. The method of claim 15, wherein: a first device couplingsubsystem is provided as a tool-less subsystem that is configured toprovide for the coupling and decoupling of the second device and thedevice chassis without the use of a tool; and a second device couplingsubsystem is provided as a tool-less subsystem that is configured toprovide for the coupling and decoupling of the second device and thedevice chassis without the use of a tool.
 19. The method of claim 17,further comprising: moving, utilizing a spring force provided by atleast one spring-loaded member that is included in the first devicecoupling subsystem, the first device at least partially out of the firstdevice slot when the first device coupling subsystem is used to decouplethe first device and the device chassis; and moving, utilizing a springforce provided by at least one spring-loaded member that is included inthe second device coupling subsystem, the second device at leastpartially out of the second device slot when the second device couplingsubsystem is used to decouple the second device and the device chassis.20. The method of claim 17, wherein: the second device couplingsubsystem providing for the coupling and decoupling of the second deviceand the device chassis independently of the coupling and decoupling ofthe first device and the device chassis includes the second devicecoupling subsystem allowing, independently of the first device beingmoved into the device chassis and secured in the first device slot aswell as unsecured from the device chassis and removed from the firstdevice slot, the second device to be moved into the device chassis andsecured in the second device slot as well as unsecured from the devicechassis and removed from the second device slot.